wayland: Handle the keymap being needed before we know about seats
authorRob Bradford <rob@linux.intel.com>
Tue, 22 Jan 2013 19:08:56 +0000 (19:08 +0000)
committerRob Bradford <rob@linux.intel.com>
Tue, 22 Jan 2013 19:12:29 +0000 (19:12 +0000)
commit2d676f32b1043523c31db36f3ccbdefe09c5ad1a
treea4792daf96c926602e5682d3eda58fe7e88430ba
parentc752cfe6a591f2d40a2694786de869085dc5a147
wayland: Handle the keymap being needed before we know about seats

In the Wayland backend implementation for gdk_display_get_keymap we enumerate
the known devices and look for an core keyboard device. These device objects
are created when we receive the capabilities for the seat. The seat
capabilities may be received after a request for the keymap so we handle this
by creating a temporary keymap which we then free later when we have the real
one.
gdk/wayland/gdkdisplay-wayland.c